Methods and systems of automatic network service initiation

ABSTRACT

Embodiments of a device and method are disclosed. In an embodiment, a method of automatic network service initiation involves pairing a first network device of a network service block (NSB) with an installer device at a customer site, at the first network device of the NSB, obtaining first network service configuration information from the installer device, performing automatic network service initiation of the first network device of the NSB based on the first network service configuration information, at a second network device of the NSB that is connected with the first network device of the NSB, obtaining address information of a cloud server from the first network device of the NSB, at the second network device of the NSB, obtaining second network service configuration information from the cloud server based on the address information, and performing automatic network service initiation of the second network device of the NSB based on the second network service configuration information.

BACKGROUND

Network deployment, for example, enterprise network deployment, at acustomer site typically involves a manual and lengthy process, which cantake several weeks to months. For example, network deployment typicallyinvolves multiple time consuming and error-prone steps, such asgathering requirements, network design, network implementation, networkoperation, and network optimization, which are manually performed bynetwork experts (e.g., network administrators). Network implementationusually includes physically racking and stacking of network devices,connecting the network devices according to a planned network topologyand manually configuring the network devices and initiating networkservices for the network devices by a network expert (e.g., a networkadministrator). However, manually configuring network devices andinitiating network services for the network devices is both timeconsuming and error-prone. In addition, getting a network expert (e.g.,a network administrator) on-site requires additional time, which canprolong the network deployment process. At some customer sites (e.g.,small offices and branches), it may be hard to find a network expert(e.g., a network administrator) to perform network device configurationfunctions. Therefore, there is a need for network implementationtechnology that can automatically initiate network services for networkdevices once the network devices are physically racked and connectedaccording to a network topology.

SUMMARY

Embodiments of a device and method are disclosed. In an embodiment, amethod of automatic network service initiation involves pairing a firstnetwork device of a network service block (NSB) with an installer deviceat a customer site, at the first network device of the NSB, obtainingfirst network service configuration information from the installerdevice, performing automatic network service initiation of the firstnetwork device of the NSB based on the first network serviceconfiguration information, at a second network device of the NSB that isconnected with the first network device of the NSB, obtaining addressinformation of a cloud server from the first network device of the NSB,at the second network device of the NSB, obtaining second networkservice configuration information from the cloud server based on theaddress information, and performing automatic network service initiationof the second network device of the NSB based on the second networkservice configuration information. Other embodiments are also described.

In an embodiment, pairing the first network device of the NSB with theinstaller device at the customer site includes pairing the first networkdevice of the NSB with the installer device at the customer site througha Bluetooth connection between the first network device of the NSB andthe installer device.

In an embodiment, the first network device of the NSB includes adistribution switch.

In an embodiment, the second network device of the NSB includes agateway, an access switch, a wireless access point, or a sensor.

In an embodiment, the NSB includes a pair of distribution switches, apair of gateways that are connected to the pair of distributionswitches, access switches that are connected to the pair of gateways,wireless access points (APs) that are connected to the access switches,and wireless sensors that wirelessly connect to the wireless APs.

In an embodiment, the method further includes at the second networkdevice of the NSB, requesting the second network service configurationinformation from the cloud server from a network address that isassigned to the second network device by the first network device.

In an embodiment, performing automatic network service initiation of thefirst network device of the NSB based on the first network serviceconfiguration information includes performing automatic network serviceinitiation of a dynamic host configuration protocol (DHCP) service, anopen shortest path first (OSPF) service, and a link layer discoveryprotocol (LLDP) service in the first network device of the NSB based onthe first network service configuration information.

In an embodiment, performing automatic network service initiation of thesecond network device of the NSB based on the second network serviceconfiguration information includes performing automatic network serviceinitiation of an OSPF service or an LLDP service in the second networkdevice of the NSB based on the second network service configurationinformation.

In an embodiment, the method further includes at the first networkdevice of the NSB, obtaining further network service configurationinformation from the cloud server based on the first network serviceconfiguration information.

In an embodiment, pairing the first network device of the NSB with theinstaller device at the customer site includes pairing the first networkdevice of the NSB with the installer device using a mobile applicationin the installer device at the customer site through a short-rangeconnection between the first network device of the NSB and the installerdevice.

In an embodiment, a method of automatic network service initiationinvolves receiving information regarding deploying an NSB at a customersite at a mobile application of an installer device, at the customersite, pairing a first network device of the NSB with the mobileapplication of the installer device through a wireless connectionbetween the first network device of the NSB and the installer device,and, from the installer device, transmitting first network serviceconfiguration information to the first network device of the NSB,wherein automatic network service initiation of the first network deviceof the NSB is performed based on the first network service configurationinformation.

In an embodiment, automatic network service initiation of a DHCPservice, an OSPF service, and an LLDP service in the first networkdevice of the NSB is performed based on the first network serviceconfiguration information.

In an embodiment, automatic network service initiation of second networkdevices of the NSB that are connected to the first network device of theNSB is performed after automatic network service initiation of the firstnetwork device of the NSB is performed.

In an embodiment, a method of automatic network service initiationinvolves at a cloud server, receiving a request for first networkservice configuration information from a first network device of an NSB,at the cloud server, transmitting the first network serviceconfiguration information to the first network device of the NSB,wherein automatic network service initiation of the first network deviceof the NSB is performed at a customer site based on the first networkservice configuration information, after automatic network serviceinitiation of the first network device of the NSB is performed, at thecloud server, receiving a request for second network serviceconfiguration information from a second network device of the NSB thatis connected to the first network device, and at the cloud server,transmitting the second network service configuration information to thesecond network device of the NSB, wherein automatic network serviceinitiation of the second network device of the NSB is performed at thecustomer site based on the second network service configurationinformation.

In an embodiment, automatic network service initiation of a DHCPservice, an OSPF service, and an LLDP service in the first networkdevice of the NSB is performed based on the first network serviceconfiguration information.

In an embodiment, automatic network service initiation of an OSPFservice or an LLDP service in the second network device of the NSB isperformed based on the second network service configuration information.

In an embodiment, the first network device of the NSB includes adistribution switch.

In an embodiment, the second network device of the NSB includes agateway, an access switch, a wireless access point, or a sensor.

In an embodiment, the NSB includes a pair of distribution switches, apair of gateways that are connected to the pair of distributionswitches, access switches that are connected to the pair of gateways,wireless access points (APs) that are connected to the access switches,and wireless sensors that wirelessly connect to the wireless APs.

In an embodiment, at the cloud server, receiving the request for thesecond network service configuration information from the second networkdevice of the NSB that is connected to the first network device includesafter the automatic network service initiation of the first networkdevice of the NSB is performed, receiving the request for the secondnetwork service configuration information from the second network deviceof the NSB with a network address that is assigned to the second networkdevice by the first network device.

Other aspects in accordance with the invention will become apparent fromthe following detailed description, taken in conjunction with theaccompanying drawings, illustrated by way of example of the principlesof the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a communications system in accordance to an embodiment ofthe invention.

FIG. 2 depicts an embodiment of a network device of the communicationssystem depicted in FIG. 1 .

FIG. 3 depicts an embodiment of an NSB of the communications systemdepicted in FIG. 1 .

FIG. 4 shows a swim-lane diagram illustrating an example procedure ofautomatic network service initiation in the communications systemdepicted in FIG. 1 .

FIG. 5 depicts an operator having an installer device wirelesslyconnecting to a first network device of an NSB.

FIG. 6 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.

FIG. 7 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.

FIG. 8 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.

FIG. 9 depicts a first network device having a network service serverand a second network device having a network service client.

FIGS. 10-14 depict results of an example operation of automatic networkservice initiation of the NSB depicted in FIG. 3 .

FIG. 15 depicts an embodiment of some network devices of the NSBdepicted in FIG. 3 .

FIG. 16 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.

FIG. 17 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.

FIG. 18 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.

Throughout the description, similar reference numbers may be used toidentify similar elements.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments asgenerally described herein and illustrated in the appended figures couldbe arranged and designed in a wide variety of different configurations.Thus, the following more detailed description of various embodiments, asrepresented in the figures, is not intended to limit the scope of thepresent disclosure, but is merely representative of various embodiments.While the various aspects of the embodiments are presented in drawings,the drawings are not necessarily drawn to scale unless specificallyindicated.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by this detailed description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

Reference throughout this specification to features, advantages, orsimilar language does not imply that all of the features and advantagesthat may be realized with the present invention should be or are in anysingle embodiment of the invention. Rather, language referring to thefeatures and advantages is understood to mean that a specific feature,advantage, or characteristic described in connection with an embodimentis included in at least one embodiment of the present invention. Thus,discussions of the features and advantages, and similar language,throughout this specification may, but do not necessarily, refer to thesame embodiment.

Furthermore, the described features, advantages, and characteristics ofthe invention may be combined in any suitable manner in one or moreembodiments. One skilled in the relevant art will recognize, in light ofthe description herein, that the invention can be practiced without oneor more of the specific features or advantages of a particularembodiment. In other instances, additional features and advantages maybe recognized in certain embodiments that may not be present in allembodiments of the invention.

Reference throughout this specification to “one embodiment”, “anembodiment”, or similar language means that a particular feature,structure, or characteristic described in connection with the indicatedembodiment is included in at least one embodiment of the presentinvention. Thus, the phrases “in one embodiment”, “in an embodiment”,and similar language throughout this specification may, but do notnecessarily, all refer to the same embodiment.

FIG. 1 depicts a communications system 100 in accordance to anembodiment of the invention. In the embodiment depicted in FIG. 1 , thecommunications system includes a cloud server 102, a network serviceblock (NSB) 150 within a customer site 114, an installer device 106, andan optional customer information portal 108. The cloud server, thenetwork service block (NSB), the installer device, and/or the customerinformation portal may be implemented in hardware (e.g., circuits),software, firmware, or a combination thereof. Although the illustratedcommunications system 100 is shown with certain components and describedwith certain functionality herein, other embodiments of thecommunications system may include fewer or more components to implementthe same, less, or more functionality. For example, in some embodiments,the communications system includes more than one cloud server, more thanone NSB, more than one customer site, more than one installer device,and/or more than one customer information portal. In another example,although the cloud server, the NSB, the customer site, the installerdevice, and the customer information portal are shown in FIG. 1 as beingconnected in certain topology, the network topology of thecommunications system 100 is not limited to the topology shown in FIG. 1.

The cloud server 102 can be used to provide at least one service to acustomer site (e.g., to the NSB 150 located at the customer site 114).The cloud server may be configured to facilitate or even provideautomatic network service initiation to network devices (e.g., the NSB150) at the customer site. Because the cloud server can facilitateautomatic network service initiation to network devices at the customersite, network implementation efficiency and accuracy can be improved. Inaddition, because the cloud server can facilitate automatic networkservice initiation to network devices at the customer site, a networkimplementation operator (e.g., an operator of the installer device 106)does not need to be a network expert. For example, a networkimplementation operator may be a layperson (e.g., a worker on-site or anend-user such as an employee) at the customer site. Consequently,network implementation of network devices can be performed withoutrelying on the expertise of an on-site network expert. For example, alayperson can perform network implementation functions in small officesand branches. Consequently, network deployment time can be shortened andthe labor cost for network deployment can be reduced. In someembodiments, the cloud server is configured to receive a request forfirst network service configuration information from a first networkdevice of the NSB 150, to transmit the first network serviceconfiguration information to the first network device of the NSB, whereautomatic network service initiation of the first network device of theNSB is performed at the customer site 114 based on the first networkservice configuration information, after the automatic network serviceinitiation of the first network device of the NSB is performed, at thecloud server, to receive a request for second network serviceconfiguration information from a second network device of the NSB thatis connected to the first network device, and to transmit the secondnetwork service configuration information to the second network deviceof the NSB, where automatic network service initiation of the secondnetwork device of the NSB is performed at the customer site based on thesecond network service configuration information. In some embodiments,automatic network service initiation of a dynamic host configurationprotocol (DHCP) service, an open shortest path first (OSPF) service, anda link layer discovery protocol (LLDP) service in the first networkdevice of the NSB is performed based on the first network serviceconfiguration information. In some embodiments, automatic networkservice initiation of an OSPF service or an LLDP service in the secondnetwork device of the NSB is performed based on the second networkservice configuration information. In some embodiments, the firstnetwork device of the NSB includes a distribution switch, while thesecond network device of the NSB includes a gateway, an access switch, awireless access point, or a sensor. In some embodiments, the cloudserver is configured to, after the automatic network service initiationof the first network device of the NSB is performed, receive the requestfor the second network service configuration information from the secondnetwork device of the NSB with a network address that is assigned to thesecond network device by the first network device. In some embodiments,the cloud server is configured to perform automatic network design for anetwork to be deployed or installed at the customer site. The cloudserver may be implemented in hardware (e.g., circuits), software,firmware, or a combination thereof. In some embodiments, the cloudserver is implemented on a server grade hardware platform, such as anx86 architecture platform. For example, the hardware platform of thecloud server may include conventional components of a computing device,such as one or more processors (e.g., CPUs), system memory, a networkinterface, storage system, and other Input/Output (I/O) devices such as,for example, a mouse and a keyboard (not shown). In some embodiments,the processor is configured to execute instructions such as, forexample, executable instructions that may be used to perform one or moreoperations described herein and may be stored in the memory and thestorage system. In some embodiments, the memory is volatile memory usedfor retrieving programs and processing data. The memory may include, forexample, one or more random access memory (RAM) modules. In someembodiments, the network interface is configured to enable the cloudserver to communicate with another device via a communication medium.The network interface may be one or more network adapters, also referredto as a Network Interface Card (NIC). In some embodiments, the cloudserver includes local storage devices (e.g., one or more hard disks,flash memory modules, solid state disks and optical disks) and/or astorage interface that enables the host to communicate with one or morenetwork data storage systems, which are used to store information, suchas executable instructions, cryptographic keys, virtual disks,configurations and other data.

In the embodiment depicted in FIG. 1 , the cloud server includes adevice deployment module 110 and a deployment database 112 configured tostore deployment data. In some embodiments, the device deployment module110 is configured to facilitate or even provide automatic networkservice initiation to network devices (e.g., the NSB 150) at thecustomer site based on, for example, a planned network design 160 thatis stored in the deployment database. The planned network design mayinclude a network topology of network devices and corresponding networkconfigurations and/or location information (e.g., building information,floor information, and/or in-building location information) of thenetwork devices. Because the device deployment module can facilitateautomatic network service initiation to network devices at the customersite, network implementation efficiency and accuracy can be improved. Inaddition, because the device deployment module can facilitate automaticnetwork service initiation to network devices at the customer site, anetwork implementation operator (e.g., an operator of the installerdevice 106) does not need to be a network expert. For example, a networkimplementation operator may be a layperson (e.g., a worker on-site or anend-user such as an employee) at the customer site. Consequently,network deployment time can be shortened and the labor cost for networkdeployment can be reduced. In some embodiments, the device deploymentmodule is configured to receive a request for first network serviceconfiguration information from a first network device of the NSB 150, totransmit the first network service configuration information to thefirst network device of the NSB, where automatic network serviceinitiation of the first network device of the NSB is performed at thecustomer site 114 based on the first network service configurationinformation, after the automatic network service initiation of the firstnetwork device of the NSB is performed, at the cloud server, to receivea request for second network service configuration information from asecond network device of the NSB that is connected to the first networkdevice, and to transmit the second network service configurationinformation to the second network device of the NSB, where automaticnetwork service initiation of the second network device of the NSB isperformed at the customer site based on the second network serviceconfiguration information. In some embodiments, the device deploymentmodule is configured to, after the automatic network service initiationof the first network device of the NSB is performed, receive the requestfor the second network service configuration information from the secondnetwork device of the NSB with a network address that is assigned to thesecond network device by the first network device. The device deploymentmodule may be configured to perform a network device deployment service(e.g., a location based network device deployment service) for networkdevices and/or to perform automatic network design for a network at thecustomer site 114. In some embodiments, the deployment database 112 isconfigured to store deployment data for a network deployed and/or to bedeployed at the customer site (e.g., a list of network devices deployedor to be deployed at the customer site). For example, the deploymentdatabase 112 is configured to store the planned network design 160,which may include a network topology of network devices (e.g., the NSB150) and corresponding network configurations and/or locationinformation (e.g., building information, floor information, and/orin-building location information) of the network devices. In someembodiments, the deployment database is configured to store a list ofnetwork devices deployed or to be deployed at the customer site anddetailed information related to the network devices, for example, devicetype information of the network devices, deployment topology informationthat defines how network devices are connected to each other, and/ordevice location information (e.g., building information, floorinformation, and in-building location information) of network devicesdeployed or to be deployed at the customer site.

The customer site 114 may include one or more buildings, and eachbuilding may include one or more floors. Network devices (e.g., the NSB150) that can be deployed at the customer site may include any type ofsuitable network devices. For example, network devices may be designatedto be deployed to a specific building, a specific floor within abuilding, and/or a specific location on a floor of a building. A networkdevice that can be deployed at the customer site may be fully orpartially implemented as an Integrated Circuit (IC) device. In someembodiments, a network device that can be deployed at the customer siteis a wired and/or wireless communications device that includes at leastone processor (e.g., a microcontroller, a digital signal processor(DSP), and/or a central processing unit (CPU)), at least one wired orwireless communications transceiver implemented in one or more logicalcircuits and/or one or more analog circuits, at least one wired orwireless communications interface and that supports at least one wiredor wireless communications protocol, and/or at least one antenna. Forexample, a network device that can be deployed at the customer site maybe compatible with Institute of Electrical and Electronics Engineers(IEEE) 802.3 protocol and/or one or more wireless local area network(WLAN) communications protocols, such as IEEE 802.11 protocol. In someembodiments, a network device that can be deployed at the customer siteis a wired communications device that is compatible with at least onewired local area network (LAN) communications protocol, such as a wiredrouter (e.g., an Ethernet router), a wired switch, a wired hub, or awired bridge device (e.g., an Ethernet bridge). In some embodiments, anetwork device that can be deployed at the customer site is a wirelessaccess point (AP) that connects to a local area network (e.g., a LAN)and/or to a backbone network (e.g., the Internet) through a wiredconnection and that wirelessly connects to wireless stations (STAs), forexample, through one or more WLAN communications protocols, such as anIEEE 802.11 protocol. In some embodiments, a network device that can bedeployed at the customer site is a wireless station (STA) thatwirelessly connects to a wireless AP. For example, the network devicemay be a laptop, a desktop personal computer (PC), a mobile phone, orother wireless device that supports at least one WLAN communicationsprotocol (e.g., an IEEE 802.11 protocol)). In some embodiments, the NSB150 is a standardized network block that includes a specific combinationof network devices. In an embodiment, a customer network may be designedas a set of one or more NSBs. In an embodiment, the NSB is thefoundational building block for network design and is replicable. Thestandardization of an NSB reduces the complexity in the network designand, hence makes the network design and Bill of Materials (BoM)generation automatable. In some embodiments, the NSB includes at leastone distribution switch (DS) or distribution layer switch that functionsas a bridge between at least one core layer switch and at least oneaccess layer switch, at least one head end (HE) or gateway, at least oneaccess switch (AS), at least one wireless access point (AP) connected tothe at least one AS, and/or at least one wireless or wired sensor thatwirelessly connects to the at least one wireless AP or is connected tothe at least one wireless AP through at least one electrical cable orwire. However, the types of network devices that can be supported by theNSB 150 are not limited to the examples described. In some embodiments,the number of HEs and DSs is constant in the NSB 150 while the number ofthe wireless APs, the ASs and the sensors in the NSB 150 varies.

In some embodiments, a first network device of the NSB 150 is configuredto pair with the installer device 106 at the customer site 114, toobtain first network service configuration information from theinstaller device, and to perform automatic network service initiation ofthe first network device of the NSB based on the first network serviceconfiguration information. In these embodiments, a second network deviceof the NSB that is connected with the first network device of the NSB isconfigured to obtain address information of a cloud server from thefirst network device of the NSB, to obtain second network serviceconfiguration information from the cloud server based on the addressinformation, and to perform automatic network service initiation of thesecond network device of the NSB based on the second network serviceconfiguration information. In some embodiments, the first network deviceof the NSB is configured to pair the first network device of the NSBwith the installer device at the customer site through a wirelessconnection (e.g., a Bluetooth connection) between the first networkdevice of the NSB and the installer device and/or a wired connectionbetween the first network device of the NSB and the installer device. Insome embodiments, the first network device of the NSB includes adistribution switch, while the second network device of the NSB includesa gateway, an access switch, a wireless access point, or a sensor. Insome embodiments, the second network device of the NSB is configured torequest the second network service configuration information from thecloud server from a network address that is assigned to the secondnetwork device by the first network device. In some embodiments, thefirst network device of the NSB is configured to perform automaticnetwork service initiation of a DHCP service, an OSPF service, and anLLDP service in the first network device of the NSB based on the firstnetwork service configuration information. In some embodiments, thesecond network device of the NSB is configured to perform automaticnetwork service initiation of an OSPF service or an LLDP service in thesecond network device of the NSB based on the second network serviceconfiguration information. In some embodiments, the first network deviceof the NSB is configured to obtain further network service configurationinformation from the cloud server based on the first network serviceconfiguration information.

FIG. 2 depicts an embodiment of a network device 204 of thecommunications system depicted in FIG. 1 . The network device 204 may bean embodiment of a network device that is included in the NSB 150depicted in FIG. 1 . However, network devices that can be included inthe NSB 150 depicted in FIG. 1 are not limited to the embodimentdepicted in FIG. 2 . The network device 204 may be any suitable type ofnetwork device. For example, the network device 204 may be adistribution switch, a gateway, an access switch, a wireless accesspoint, or a sensor, described in details with reference to FIG. 3 . Inthe embodiment depicted in FIG. 2 , a network device 204 includes awireless and/or wired transceiver 232, a controller 234 operablyconnected to the transceiver 232, at least one optional antenna 236operably connected to the transceiver 232, and at least one optionalnetwork port 238 operably connected to the transceiver 232. In someembodiments, the transceiver 232 includes a physical layer (PHY) device.The transceiver 232 may be any suitable type of transceiver. Forexample, the transceiver 232 may be a short-range communicationstransceiver (e.g., a Bluetooth) or a LAN transceiver (e.g., atransceiver compatible with an IEEE 802.11 protocol). In someembodiments, the network device 204 includes multiple transceivers, forexample, a short-range communications transceiver (e.g., a Bluetooth)and a LAN transceiver (e.g., a transceiver compatible with an IEEE802.11 protocol). The controller 234 may be configured to control thetransceiver 232 to process to process packets received through theantenna 236 and/or the network port 238 and/or to generate outgoingpackets to be transmitted through the antenna 236 and/or the networkport 238. In some embodiments, the controller 234 is configured toperform automatic network service initiation of the network device 204based on network service configuration information, which may bereceived from the installer device 106 and/or the cloud server 102. Forexample, the controller 234 may be configured to perform automaticnetwork service initiation of a dynamic host configuration protocol(DHCP) service, an open shortest path first (OSPF) service, and/or alink layer discovery protocol (LLDP) in the network device 204 based onnetwork service configuration information, which may be received fromthe installer device 106 and/or the cloud server 102. The antenna 236may be any suitable type of antenna. For example, the antenna 236 may bean induction type antenna such as a loop antenna or any other suitabletype of induction type antenna. However, the antenna 236 is not limitedto an induction type antenna. The network port 238 may be any suitabletype of port. For example, the network port 238 may be a local areanetwork (LAN) network port such as an Ethernet port. However, thenetwork port 238 is not limited to LAN network ports.

FIG. 3 depicts an embodiment of an NSB 350 for the customer site 114.The NSB 350 depicted in FIG. 3 is one possible embodiment of the NSB 150at the customer site 114 depicted in FIG. 1 . However, the NSB 150 atthe customer site 114 depicted in FIG. 1 are not limited to theembodiment shown in FIG. 3 . In some embodiments, the NSB 350 is a basicbuilding block for providing connectivity as a service and is areplicable block that can be scaled (e.g., expanded) to meet anydeployment. In the embodiment depicted in FIG. 3 , the NSB 350 includesa pair of distribution switches (DSs) or distribution layer switches352-1, 352-2 that are aggregation switches functioning as a bridgebetween core layer switches and access layer switches, a pair of headends (HEs) or gateways 354-1, 354-2, a number of access switches (ASs)356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, 356-8 connected inrings 358-1, 358-2 that directly interact with lower level devices(e.g., wireless APs), a number of wireless APs 360-1, 360-2, 360-3,360-4, 360-5, 360-6 connected to the ASs, and a number of wirelesssensors 362-1, 362-2, 362-3 that wirelessly connect to the wireless APs.In some embodiments, the number of HEs and DSs is constant in the NSB350 while the number of the wireless APs, the ASs and the sensors in theNSB 350 varies.

Turning back to the communications system 100 depicted in FIG. 1 , theinstaller device 106 may be any type of suitable network device that isused by an operator to facilitate the deployment of network devices(e.g., the NSB 150) at the customer site 114. In some embodiments, theinstaller device may be fully or partially implemented as an IC device.In some embodiments, the installer device is a wireless communicationsdevice that includes at least one processor (e.g., a microcontroller, aDSP, and/or a CPU), at least one wireless communications transceiver, atleast one wireless communications interface, and/or at least one antennaand that supports at least one wireless communications protocol. In someembodiments, the installer device is a handheld wireless device, such asa cellular phone or a mobile phone (e.g., a smart phone), a padcomputer, a Personal Digital Assistant (PDA) etc. that supports one ormore radio frequency (RF) communications protocols, including withoutlimitation, Bluetooth, The Global System for Mobile Communications(GSM), Universal Mobile Telecommunications System (UMTS), Code DivisionMultiple Access (CDMA), Worldwide Interoperability for Microwave Access(WiMax) and communications protocols as defined by the 3rd GenerationPartnership Project (3GPP) or the 3rd Generation Partnership Project 2(3GPP2), 4G Long Term Evolution (LTE), the fifth generation technologystandard for broadband cellular network (5G), and IEEE 802.16 standardsbodies and/or one or more wireless local area network (WLAN)communications protocols, such as an IEEE 802.11 protocol. For example,the installer device 106 is a wireless communications device, such as ahandheld wireless device (e.g., cellular phone or a mobile phone) thatsupports multiple communications protocols, which may include at leastone cellular communications protocol and at least short-rangecommunications protocol (e.g., Bluetooth). In some embodiments, serviceinitiation software or App is installed on the installer device 106(e.g., a mobile phone or tablet). Because automatic network serviceinitiation of network devices at the customer site can be facilitated bythe cloud server 102 (e.g., the device deployment module 110), networkimplementation efficiency and accuracy can be improved. In addition,because automatic network service initiation of network devices at thecustomer site can be facilitated by the cloud server 102 (e.g., thedevice deployment module 110), an operator of the installer device doesnot need to be a network expert. For example, an operator of theinstaller device may be a non-network savvy person such as a contractor,a technician, or an end-user at the customer site 114. Consequently,network implementation of network devices can be performed withoutrelying on the expertise of an on-site network expert. For example, alayperson can perform network implementation functions in small officesand branches. Consequently, network deployment time can be shortened andthe labor cost for network deployment can be reduced. In someembodiments, the installer device is configured to receive informationregarding deploying the NSB 150 at the customer site 114 at a mobileapplication of the installer device, at the customer site, to pair afirst network device of the NSB with the mobile application of theinstaller device through a short range connection (e.g., a Bluetoothconnection) between the first network device of the NSB and theinstaller device, and from the installer device, to transmit firstnetwork service configuration information to the first network device ofthe NSB. Automatic network service initiation of the first networkdevice of the NSB is performed based on the first network serviceconfiguration information. In some embodiments, automatic networkservice initiation of a DHCP service, an OSPF service, and an LLDPservice in the first network device of the NSB is performed based on thefirst network service configuration information. In some embodiments,automatic network service initiation of second network devices of theNSB that are connected to the first network device of the NSB isperformed after automatic network service initiation of the firstnetwork device of the NSB is performed.

The customer information portal 108, which may be optional to thecommunications system 100, is configured to receive customerinformation. In some embodiments, the customer information portalincludes a user interface that allows a customer to input informationassociated with network design for the customer site 114, such as one ormore specific requirements or restrictions. For example, the userinterface (e.g., a graphical user interface (GUI)) may allow a customerto input information associated with network design for the customersite. The customer information portal may be implemented in hardware(e.g., circuits), software, firmware, or a combination thereof.

FIG. 4 shows a swim-lane diagram illustrating an example procedure ofautomatic network service initiation in the communications system 100depicted in FIG. 1 . In this automatic network service initiationprocedure, network services are automatically initiated for networkdevices (e.g., the NSB 150) deployed in the customer site 114. In someembodiments, an operator 120 of the installer device 106 connects afirst network device (e.g., a distribution switch (DS)) of the NSB 150to a router at the customer site and powers on the first network deviceprior to the automatic network service initiation procedure. In theseembodiments, after one or more network services are automaticallyinitiated for the first network device of the NSB, one or more networkservices are automatically initiated for other network elements of theNSB once these network elements are connected to the first networkdevice directly or indirectly.

In operation 402, the cloud server 102 (e.g., the device deploymentmodule 110) transmits deployment information to the installer device 106that is operated by the operator 120. The operator may not be a networkexpert and may possess only basic knowledge of networking. In someembodiments, the deployment information includes a list of networkdevices deployed or to be deployed at the customer site and detailedinformation related to the network devices, for example, device typeinformation of the network devices, deployment topology information thatdefines how network devices are connected to each other, and/or devicelocation information (e.g., building information, floor information, andin-building location information) of network devices deployed or to bedeployed at the customer site. The device deployment module may transmitthe deployment information to a mobile app in the installer device. Forexample, the installer device is a handheld wireless device, such as acellular phone or a mobile phone (e.g., a smart phone), a pad computer,a PDA etc., and the mobile app is a mobile application from anapplication store (e.g., Android Market, Apple App Store, AmazonAppstore, carrier applications stores, etc.).

In operation 404, a pairing request is received at the installer device106 from a first network device of the NSB 150. In some embodiments, thepairing request is received from a short-range communications connectionbetween the first network device of the NSB and the installer device. Inan embodiment, the installer device is paired with the first networkdevice of the NSB through a Bluetooth connection to initiate a networkservice in the network device. In some embodiments, when the firstnetwork device of the NSB is connected to a router at the customer site114, the local software on the first network device may turn on itsBluetooth module to “ready to pair” mode and pairs with the installerdevice over Bluetooth. For example, after the installer device connectsthe first network device to a router at the customer site, the operator120 of the installer device goes physically near the first networkdevice and pairs the installer device with the first network device overBluetooth. In some embodiments, a paring request is transmitted from thefirst network device of the NSB to the installer device to setup aconnection (e.g., a short-range communications connection) between thefirst network device of the NSB and the installer device. In someembodiments, the first network device of the NSB is a distributionswitch (DS), for example, the DS 352-1 or 352-2 of the NSB 350 depictedin FIG. 3 . For example, after one or more network services areautomatically initiated for a DS of the NSB, corresponding networkservices are automatically initiated for other network elements of theNSB once these network elements are connected to the DS directly orindirectly.

FIG. 5 depicts an operator 520 having an installer device 506 wirelesslyconnecting to a first network device 504 of the NSB 150. The networkdevice 504 depicted in FIG. 5 may be an embodiment of the DS 352-1 or352-2 depicted in FIG. 3 , while the installer device 506 depicted inFIG. 5 may be an embodiment of the installer device 106 depicted in FIG.1 . However, the DS 352-1 or 352-2 depicted in FIG. 3 and the installerdevice 106 depicted in FIG. 1 are not limited to the embodiment shown inFIG. 5 . In the embodiment depicted in FIG. 5 , the first network device504 contains an access module 540 configured to communicate with theinstaller device 506 (e.g., a mobile app at the installer device 506)that is operated by the operator 520. The access module may beimplemented in hardware (e.g., circuits), software, firmware, or acombination thereof. In an example operation, the installer device 506(e.g., a cellular phone or a mobile phone (e.g., a smart phone)) ispaired with the access module (e.g., an access application) of the firstnetwork device 504 through a short-range communications link 544 (e.g.,a Bluetooth communications link).

Turning back to the swim-lane diagram shown in FIG. 4 , in operation406, the installer device 106 that is operated by the operator 120transmits configuration information to the first network device of theNSB 150, for example, through a short-range communications link (e.g., aBluetooth connection). In some embodiments, the configurationinformation is included or derived from the deployment informationtransmitted from the cloud server 102 (e.g., the device deploymentmodule 110) to the installer device 106 and/or input by the operator 120of the installer device 106. In some embodiments, the configurationinformation includes network address configuration information (e.g.,Internet Protocol (IP) address configuration information) for the firstnetwork device of the NSB 150. For example, the configurationinformation includes at least one port number of at least one DS portthat is connected to at least one corresponding port of a router at thecustomer site 114, static IP address for the DS port(s) connected tocustomer router ports(s), a customer router side IP address, a domainname system (DNS) server IP address, an IP address of DS loopbackinterface, a peer DS loopback interface IP address, a fully qualifieddomain name (FQDN) of a cloud activation server (e.g., the cloud server102), and/or a dynamic host configuration protocol (DHCP) addressscope/range. The installer device may transmit configuration informationto the first network device of the NSB 150 using a mobile app in theinstaller device. In some embodiments, the installer device 106transmits network address configuration information to a DS of the NSB150 (e.g., the DS 352-1 or 352-2 of the NSB 350 depicted in FIG. 3 ),for example, through a short-range communications link (e.g., aBluetooth connection).

In operation 408, the first network device of the NSB 150 may requestfurther configuration information from the cloud server 102 (e.g., thedevice deployment module 110) and/or another cloud server, for example,based on the configuration information (e.g., network addressconfiguration information) received from the installer device 106. Insome embodiments, the further configuration information includes openshortest path first (OSPF) configuration and/or link layer discoveryprotocol (LLDP) configuration for the first network device of the NSB150. In operation 410, the requested further configuration informationmay be transmitted to the first network device of the NSB 150 from thecloud server 102 (e.g., the device deployment module 110) and/or anothercloud server.

In operation 412, a service initiation (e.g., initiation of OSPF serviceand/or LLDP service) of the first network device of the NSB 150 isimplemented, for example, based on the received configurationinformation and/or the received further configuration information. Insome embodiments, a DHCP server is enabled on the first network device(e.g., a DS) of the NSB. In an embodiment, a DHCP server is enabled ontwo DSs of the NSB 150 (e.g., the DSs 352-1, 352-2 of the NSB 350depicted in FIG. 3 ) and one of the two DSs is elected as Active and theother one of the two DSs is elected as Standby.

After one or more network services are automatically initiated for thefirst network device of the NSB 150, one or more network services areautomatically initiated for other network elements (e.g., HEs, ASs, APs,and/or sensors) of the NSB once these network elements are connected tothe first network device of the NSB 150 directly or indirectly. Forexample, in operation 414, a second network device of the NSB 150, whichmay be a HE (e.g., the HE 354-1 or 354-2 depicted in FIG. 3 ), an AS(e.g., the AS 356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, or 356-8depicted in FIG. 3 ), an AP (e.g., the wireless AP 360-1, 360-2, 360-3,360-4, 360-5, or 360-6 depicted in FIG. 3 ), or a sensor (e.g., thewireless sensor 362-1, 362-2, or 362-3 depicted in FIG. 3 ), isconnected to the first network device of the NSB 150. In someembodiments, when the second network device of the NSB 150 is connectedto the first network device of the NSB 150, the second network device ofthe NSB 150 obtains address information (e.g., IP address configurationinformation) of a cloud server (e.g., the cloud server 102) from thefirst network device of the NSB. In some embodiments, when the secondnetwork device of the NSB 150 is connected to the first network deviceof the NSB 150, the second network device of the NSB 150 receivesnetwork address configuration information (e.g., IP addressconfiguration information), such as a pre-allocated IP address for thesecond network device of the NSB 150, a corresponding DNS server IPaddress, and/or an FQDN of a cloud server (e.g., the cloud server 102).

In operation 416, the second network device of the NSB 150 may requestservice configuration information from the cloud server 102 (e.g., thedevice deployment module 110) and/or another cloud server, for example,based on network address configuration information received from thefirst network device of the NSB 150. In some embodiments, the serviceconfiguration information includes OSPF configuration and/or LLDPconfiguration for the second network device of the NSB 150. In operation418, the requested service configuration information may be transmittedto the second network device of the NSB 150 from the cloud server 102(e.g., the device deployment module 110) and/or another cloud server. Inoperation 420, a service initiation (e.g., initiation of OSPF serviceand/or LLDP service) of the second network device of the NSB 150 isdone, for example, based on the received configuration information. Insome embodiments, an OSPF service and/or an LLDP service is enabled onthe second network device of the NSB, which may be, for example, a HE(e.g., the HE 354-1 or 354-2 depicted in FIG. 3 ), an AS (e.g., the AS356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, or 356-8 depicted inFIG. 3 ), an AP (e.g., the wireless AP 360-1, 360-2, 360-3, 360-4,360-5, or 360-6 depicted in FIG. 3 ), or a sensor (e.g., the wirelesssensor 362-1, 362-2, or 362-3 depicted in FIG. 3 .

FIG. 6 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.According to the method, at block 602, a first network device of anetwork service block (NSB) is paired with an installer device at acustomer site. In some embodiments, the first network device of the NSBis paired with the installer device at the customer site through aBluetooth connection between the first network device of the NSB and theinstaller device. In some embodiments, the first network device of theNSB is paired with the installer device using a mobile application inthe installer device at the customer site through a short-rangeconnection between the first network device of the NSB and the installerdevice. In some embodiments, the NSB includes a pair of distributionswitches, a pair of gateways that are connected to the distributionswitches, access switches that are connected to the gateways, wirelessaccess points (APs) that are connected to the access switches, andwireless sensors that wirelessly connect to the wireless APs. In someembodiments, the first network device of the NSB includes a distributionswitch. At block 604, at the first network device of the NSB, firstnetwork service configuration information is obtained from the installerdevice. At block 606, automatic network service initiation of the firstnetwork device of the NSB is performed based on the first networkservice configuration information. In some embodiments, the automaticnetwork service initiation of a dynamic host configuration protocol(DHCP) service, an open shortest path first (OSPF) service, and a linklayer discovery protocol (LLDP) service in the first network device ofthe NSB is performed based on the first network service configurationinformation. At block 608, at a second network device of the NSB that isconnected with the first network device of the NSB, address informationof a cloud server is obtained from the first network device of the NSB.In some embodiments, the second network device of the NSB includes agateway, an access switch, a wireless access point, or a sensor. Atblock 610, at the second network device of the NSB, second networkservice configuration information is obtained from the cloud serverbased on the address information. At block 612, automatic networkservice initiation of the second network device of the NSB is performedbased on the second network service configuration information. In someembodiments, the automatic network service initiation of an OSPF serviceor an LLDP service in the second network device of the NSB is performedbased on the second network service configuration information. In someembodiments, at the first network device of the NSB, further networkservice configuration information is obtained from the cloud serverbased on the first network service configuration information. In someembodiments, at the second network device of the NSB, the second networkservice configuration information is requested from the cloud serverfrom a network address that is assigned to the second network device bythe first network device. The operations 602, 604, 606, 608, 610, 612 inthe flow diagram of FIG. 6 may correspond to the operations 404, 406,412, 414, 418, 420 in the swim-lane diagram of FIG. 4 . The NSB may besimilar to, the same as, or a component of the NSB 150 depicted in FIG.1 and/or the NSB 350 depicted in FIG. 3 . The cloud server may besimilar to, the same as, or a component of the cloud server 102 depictedin FIG. 1 . The first network device may be similar to, the same as, ora component of the DSs 352-1, 352-2 of the NSB 350 depicted in FIG. 3and/or the network device 504 depicted in FIG. 5 . The second networkdevice may be similar to, the same as, or a component of the HEs 354-1,354-2 of the NSB 350, the ASs 356-1, 356-2, 356-3, 356-4, 356-5, 356-6,356-7, 356-8, the wireless APs 360-1, 360-2, 360-3, 360-4, 360-5, 360-6,and/or the wireless sensors 362-1, 362-2, 362-3 depicted in FIG. 3 . Theinstaller device may be similar to, the same as, or a component of theinstaller device 106 depicted in FIG. 1 . The customer site may besimilar to, the same as, or a component of the customer site 114depicted in FIG. 1 .

FIG. 7 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.According to the method, at block 702, information regarding deploying anetwork service block (NSB) at a customer site is received at a mobileapplication of an installer device. At block 704, at the customer site,a first network device of the NSB is paired with the mobile applicationof the installer device through a wireless (e.g., Bluetooth) connectionbetween the first network device of the NSB and the installer device. Atblock 706, from the installer device, first network serviceconfiguration information is transmitted to the first network device ofthe NSB, where automatic network service initiation of the first networkdevice of the NSB is performed based on the first network serviceconfiguration information. In some embodiments, automatic networkservice initiation of a DHCP service, an OSPF service, and an LLDPservice in the first network device of the NSB is performed based on thefirst network service configuration information. In some embodiments,automatic network service initiation of second network devices of theNSB that are connected to the first network device of the NSB isperformed after automatic network service initiation of the firstnetwork device of the NSB is performed. The operations 702, 704, 706 inthe flow diagram of FIG. 7 may correspond to the operations 402, 404,406 in the swim-lane diagram of FIG. 4 . The NSB may be similar to, thesame as, or a component of the NSB 150 depicted in FIG. 1 and/or the NSB350 depicted in FIG. 3 . The first network device may be similar to, thesame as, or a component of the DSs 352-1, 352-2 of the NSB 350 depictedin FIG. 3 and/or the network device 504 depicted in FIG. 5 . Theinstaller device may be similar to, the same as, or a component of theinstaller device 106 depicted in FIG. 1 . The customer site may besimilar to, the same as, or a component of the customer site 114depicted in FIG. 1 .

FIG. 8 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.According to the method, at block 802, at a cloud server, a request forfirst network service configuration information is received from a firstnetwork device of a network service block (NSB). At block 804, at thecloud server, the first network service configuration information istransmitted to the first network device of the NSB, where automaticnetwork service initiation of the first network device of the NSB isperformed at a customer site based on the first network serviceconfiguration information. In some embodiments, the first network deviceof the NSB includes a distribution switch. In some embodiments, theautomatic network service initiation of a DHCP service, an OSPF service,and an LLDP service in the first network device of the NSB is performedbased on the first network service configuration information. In someembodiments, the NSB includes a pair of distribution switches, a pair ofgateways that are connected to the distribution switches, accessswitches that are connected to the gateways, wireless APs that areconnected to the access switches, and wireless sensors that wirelesslyconnect to the wireless APs. At block 806, after the automatic networkservice initiation of the first network device of the NSB is performed,at the cloud server, a request for second network service configurationinformation is received from a second network device of the NSB that isconnected to the first network device. In some embodiments, the secondnetwork device of the NSB includes a gateway, an access switch, awireless access point, or a sensor. In some embodiments, after theautomatic network service initiation of the first network device of theNSB is performed, the request for the second network serviceconfiguration information is received from the second network device ofthe NSB with a network address that is assigned to the second networkdevice by the first network device. At block 808, at the cloud server,the second network service configuration information is transmitted tothe second network device of the NSB, where automatic network serviceinitiation of the second network device of the NSB is performed at thecustomer site based on the second network service configurationinformation. In some embodiments, the automatic network serviceinitiation of an OSPF service or a LLDP service in the second networkdevice of the NSB is performed based on the second network serviceconfiguration information. The operations 802, 804, 806, 808 in the flowdiagram of FIG. 8 may correspond to the operations 408, 410, 416, 418 inthe swim-lane diagram of FIG. 4 . The NSB may be similar to, the sameas, or a component of the NSB 150 depicted in FIG. 1 and/or the NSB 350depicted in FIG. 3 . The cloud server may be similar to, the same as, ora component of the cloud server 102 depicted in FIG. 1 . The firstnetwork device may be similar to, the same as, or a component of the DSs352-1, 352-2 of the NSB 350 depicted in FIG. 3 and/or the network device504 depicted in FIG. 5 . The second network device may be similar to,the same as, or a component of the HEs 354-1, 354-2 of the NSB 350, theASs 356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, 356-8, the wirelessAPs 360-1, 360-2, 360-3, 360-4, 360-5, 360-6, and/or the wirelesssensors 362-1, 362-2, 362-3 depicted in FIG. 3 . The customer site maybe similar to, the same as, or a component of the customer site 114depicted in FIG. 1 .

FIG. 9 depicts a first network device 904 having a network serviceserver 940 and a second network device 954 having a network serviceclient 990. The first and second network devices 904, 954 depicted inFIG. 9 may be embodiments of network devices that are included in theNSB 150 depicted in FIG. 1 and/or the NSB 350 depicted in FIG. 3 .However, network devices that can be included in the NSB 150 depicted inFIG. 1 and/or the NSB 350 depicted in FIG. 3 are not limited to theembodiments depicted in FIG. 9 . The first and second network devices904, 954 depicted in FIG. 9 may be any suitable type of network devices.For example, the first network device 904 may be a distribution switch,while the second network device 954 may be a gateway, an access switch,a wireless access point, or a sensor.

In the embodiment depicted in FIG. 9 , the first network device 904includes a wireless and/or wired transceiver 932, a controller 934operably connected to the transceiver 932, at least one optional antenna936 operably connected to the transceiver 932, and at least one optionalnetwork port 938 operably connected to the transceiver 932. In someembodiments, the transceiver 932 includes a PHY device. The transceiver932 may be any suitable type of transceiver. For example, thetransceiver 932 may be a short-range communications transceiver (e.g., aBluetooth) or a LAN transceiver (e.g., a transceiver compatible with anIEEE 802.11 protocol). In some embodiments, the first network device 904includes multiple transceivers, for example, a short-rangecommunications transceiver (e.g., a Bluetooth) and a LAN transceiver(e.g., a transceiver compatible with an IEEE 802.11 protocol). Thecontroller 934 may be configured to control the transceiver 932 toprocess to process packets received through the antenna 936 and/or thenetwork port 938 and/or to generate outgoing packets to be transmittedthrough the antenna 936 and/or the network port 938. In someembodiments, the controller 934 is configured to perform automaticnetwork service initiation of the first network device 904 based onnetwork service configuration information, which may be received fromthe installer device 106 and/or the cloud server 102. For example, thecontroller 934 may be configured to perform automatic network serviceinitiation of a dynamic host configuration protocol (DHCP) service, anopen shortest path first (OSPF) service, and/or a link layer discoveryprotocol (LLDP) in the first network device 904 based on network serviceconfiguration information, which may be received from the installerdevice 106 and/or the cloud server 102. The antenna 936 may be anysuitable type of antenna. For example, the antenna 936 may be aninduction type antenna such as a loop antenna or any other suitable typeof induction type antenna. However, the antenna 936 is not limited to aninduction type antenna. The network port 938 may be any suitable type ofport. For example, the network port 938 may be a LAN network port suchas an Ethernet port. However, the network port 938 is not limited to LANnetwork ports. In the embodiment depicted in FIG. 9 , the second networkdevice 954 includes a wireless and/or wired transceiver 982, acontroller 984 operably connected to the transceiver 982, at least oneoptional antenna 986 operably connected to the transceiver 982, and atleast one optional network port 988 operably connected to thetransceiver 982. In some embodiments, the transceiver 982 includes a PHYdevice. The transceiver 982 may be any suitable type of transceiver. Forexample, the transceiver 982 may be a short-range communicationstransceiver (e.g., a Bluetooth) or a LAN transceiver (e.g., atransceiver compatible with an IEEE 802.11 protocol). The controller 984may be configured to control the transceiver 982 to process to processpackets received through the antenna 986 and/or the network port 988and/or to generate outgoing packets to be transmitted through theantenna 986 and/or the network port 988. In some embodiments, thecontroller 984 is configured to perform automatic network serviceinitiation of the second network device 954 based on network serviceconfiguration information, which may be received from the cloud server102. For example, the controller 984 may be configured to performautomatic network service initiation of an OSPF service and/or an LLDPin the second network device 954 based on network service configurationinformation, which may be received from the cloud server 102. Theantenna 986 may be any suitable type of antenna. For example, theantenna 986 may be an induction type antenna such as a loop antenna orany other suitable type of induction type antenna. However, the antenna986 is not limited to an induction type antenna. The network port 988may be any suitable type of port. For example, the network port 988 maybe a LAN network port such as an Ethernet port. However, the networkport 988 is not limited to LAN network ports.

In the embodiment depicted in FIG. 9 , the first network device 904includes the network service server 940, which may be implemented inhardware (e.g., circuits), software, firmware, or a combination thereof.In some embodiments, the network service server 940 is implementedwithin the controller 934. However, in other embodiments, the networkservice server 940 may be partially or completely implemented externallyto the controller 934. In the embodiment depicted in FIG. 9 , the secondnetwork device 954 includes the network service client 990, which may beimplemented in hardware (e.g., circuits), software, firmware, or acombination thereof. In some embodiments, the network service client 990is implemented within the controller 984. However, in other embodiments,the network service client 990 may be partially or completelyimplemented externally to the controller 984. The network service client990 may communicate with the network service server 940 through a wiredconnection 946 between the network port 938 of the first network device904 and the network port 988 of the second network device 954 and/or awireless connection 944 between the antenna 936 of the first networkdevice 904 and the antenna 986 of the second network device 954. In theembodiment depicted in FIG. 9 , the network service server 940 isconfigured to assign network addresses and/or provide other networkinformation (e.g., a cloud server address) to network service clientsand the network service client 990 is configured to request networkaddress and other information from the network service server 940. Insome embodiments, the network service server 940 is a DHCP serverconfigured to assign IP addresses and/or provide other networkinformation (e.g., an IP address of a DNS server, an IP address ofanother network device (e.g., an intermediate device), and/or a cloudserver address) to DHCP clients and the network service client 990 is aDHCP client configured to request IP address and other information fromthe network service server 940.

An example operation of automatic network service initiation of the NSB350 depicted in FIG. 3 is described with reference to FIGS. 10-14 . Inthis example operation, network services are first automaticallyinitiated for the DSs 352-1, 352-2 of the NSB 350. Subsequently, networkservices are automatically initiated for the HEs 354-1, 354-2 of the NSB350, for the ASs 356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, 356-8,for the wireless APs 360-1, 360-2, 360-3, 360-4, 360-5, 360-6, and forthe wireless sensors 362-1, 362-2, 362-3, respectively, once thesenetwork elements are connected to the DSs 352-1, 352-2 directly orindirectly. Prior to this example operation, the operator 120 of theinstaller device 106 connects the DSs 352-1, 352-2 of the NSB 350 to arouter at the customer site 114 and powers on the DSs 352-1, 352-2.

FIG. 10 depicts a result of a first step of the example operation. Inthis first step, once each of the DSs 352-1, 352-2 of the NSB 350performs a secure boot, each of the DSs 352-1, 352-2 may pair with amobile app in the installer device 106 via Bluetooth. The mobile app'sinterface can be used to configure the configuration for each of the DSs352-1, 352-2 (e.g., by the operator 120 of the installer device 106and/or automatically configured by the installer device 106 based onnetwork configuration information received from the cloud server 102),which includes a port number of a DS port that is connected to acorresponding port of a router at the customer site 114, a static IPaddress for the DS port(s) connected to customer router ports(s), acustomer router side IP address, a domain name system (DNS) server IPaddress, an IP address of DS loopback interface, a peer DS loopbackinterface IP address, a FQDN of a cloud activation server (e.g., thecloud server 102 or another cloud server), and a dynamic hostconfiguration protocol (DHCP) address scope/range. DHCP servers may beenabled on both of the DSs 352-1, 352-2 and one DHCP server of the DSs352-1, 352-2 is elected as active and the other DHCP server of the DSs352-1, 352-2 is elected as standby. Based on the configuration, the DSs352-1, 352-2 may request and receive OSPF and LLDP configurations fromthe cloud server 102 or another cloud server. Once the link between theDSs 352-1, 352-2 is setup, OSPF and LLDP in adjacencies are formed onthe link.

FIG. 11 depicts a result of a second step of the example operation thattakes place after the first step. In this second step, after each of theHEs 354-1, 354-2 of the NSB 350 completes a successful bootup, each ofthe HEs 354-1, 354-2 may send a DHCP request using a DHCP client on itsconnected interface. In some embodiments, each HE uses DHCP option 60 ina DHCP request to indicate that the request is from a HE. The activeDHCP server on the DSs 352-1, 352-2 may return a pre-allocated IPaddress that may be assigned to a loopback interface and a DNS server IPaddress, and return, using a sub-option (e.g., option 43), the FQDN of acloud server (e.g., the cloud server 102 or other cloud server). Each ofthe HEs 354-1, 354-2 may reach out to the corresponding cloud sever toobtain its configuration (e.g., LLDP configuration) on the HE. OSPFservice is not enabled on the HEs. Each of the HEs 354-1, 354-2 may alsoestablish a gRPC Remote Procedure Calls (gRPC) channel to acorresponding DS 352-1 or 352-2. Each of the HEs 354-1, 354-2 may alsoconfigure a default route to a corresponding DS 352-1 or 352-2 in itsrouting table, the next_hop for the default route can be derived fromthe LLDP configuration.

FIG. 12 depicts a result of a third step of the example operation thattakes place after the second step. In this third step, out of the ASs356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, 356-8, the ASs 356-1,356-5 that are directly connected to the DSs 352-1, 352-2 is broughtinto service first. Each AS 356-1 or 356-5, after successful bootup,sends a DHCP request using its DHCP client on its interface connected toa corresponding DS 352-1 or 352-2 to a DHCP server at the DS 352-1 or352-2. Each AS 356-1 or 356-5 may use DHCP option 60 to identify itselfas an AS in the DHCP request. Each AS 356-1 or 356-5 may reach out to acloud server (e.g., the cloud server 102 or other cloud server) toobtain its configuration (e.g., LLDP and OSPF configuration). Each AS356-1 or 356-5 may also receive a “DHCP helper” configuration andprograms the configuration in all its access interfaces and theinterfaces that connect the other access switches in the ring 358-1 or358-2. The DHCP server on a corresponding DS 352-1 or 352-2 may returnan IP address of the AS (e.g., assigned to loopback) and a DNS server IPaddress and return, using a sub-option (e.g., option 43), the FQDN of acloud server (e.g., the cloud server 102 or other cloud server) and acorresponding HE IP address.

FIG. 13 depicts a result of a fourth step of the example operation thattakes place after the third step. In this fourth step, all downstreamASs 356-2, 356-3, 356-4, 356-6, 356-7, 356-8 in the ring 358-1 or 358-2that are not directly connected to a corresponding DS 352-1 or 352-2 maysend a DHCP request on the “ring interfaces” with option 60 identifyingthemselves. The DHCP helper configuration on the upstream AS 356-1 or356-5 may relay the DHCP request to the DHCP server on a correspondingDS 352-1 or 352-2. The DHCP server on a corresponding DS 352-1 or 352-2may return an IP address of the AS (e.g., assigned to loopback) and aDNS server IP address and return, using a sub-option (e.g., option 43),the FQDN of a cloud server (e.g., the cloud server 102 or other cloudserver), and a corresponding HE IP address. All downstream ASs 356-2,356-3, 356-4, 356-6, 356-7, 356-8 may reach out to the correspondingcloud server to obtain their configuration and turn on OSPF and LLDP onthe ring interfaces and the uplink interfaces to the corresponding DS(e.g., LLDP and OSPF are not enabled on the access ports of the accessswitch). All the ASs may also establish a gRPC channel to acorresponding HE and a Generic Routing Encapsulation (GRE) tunnel to thecorresponding HE.

FIG. 14 depicts a result of a fifth step of the example operation thattakes place after the fourth step. In this fifth step, each of thewireless APs 360-1, 360-2, 360-3, 360-4, 360-5, 360-6 may receive itspower from a corresponding power over ethernet (PoE) port of acorresponding AS 356-2, 356-3, 356-4, 356-6, 356-7, or 356-8. Each AP,after successful boot, sends a DHCP request through its DHCP client. Forexample, each AP may identify itself in the DHCP request using option60. A corresponding AS relays the DHCP request to a corresponding DHCPserver running on the DS 352-1 or 352-2. In some embodiments, amechanism is implemented to differentiate an AP DHCP request from aclient-end point DHCP request on an access port such that the client endpoint DHCP requests can enter a GRE tunnel. The corresponding DHCPserver on the corresponding DS may return an IP address of the AP(assigned to AP loopback) and a DNS Server IP address and return, usinga sub-option (e.g., option 43), a HE IP address, and the FQDN of a cloudserver (e.g., the cloud server 102 or other cloud server). The APs mayreach out to the cloud server to obtain their configuration and run LLDPon the uplinks connected to a corresponding AS. Each AP may alsoestablish a gRPC channel to a corresponding HE and a GRE tunnel to thecorresponding HE. Similarly, network services are automaticallyinitiated for the wireless sensors 362-1, 362-2, 362-3.

FIG. 15 depicts an embodiment of the DS 352-1, the HE 354-1, the AS356-1, the AS 356-4, the wireless AP 360-3, and the wireless sensor362-1 of the NSB 350 depicted in FIG. 3 . However, the DS 352-1, the HE354-1, the AS 356-1, the AS 356-4, the wireless AP 360-3, and thewireless sensor 362-1 depicted in FIG. 3 are not limited to theembodiments depicted in FIG. 15 . In the embodiment depicted in FIG. 15, the DS 352-1 includes a wired transceiver 1532, a controller 1534operably connected to the transceiver 1532 that includes a DHCP server1540, and network ports 1538-1, 1538-2 operably connected to thetransceiver 1532. The HE 354-1 includes a wired transceiver 1582, acontroller 1584 operably connected to the transceiver 1582 that includesa DHCP client 1590, and a network port 1588-1 operably connected to thetransceiver 1582. The AS 356-1 includes a wired transceiver 1542, acontroller 1544 operably connected to the transceiver 1542 that includesa DHCP client 1592, and network ports 1548-1, 1548-2 operably connectedto the transceiver 1542. The AS 356-4 includes a wired transceiver 1552,a controller 1554 operably connected to the transceiver 1552 thatincludes a DHCP client 1594, and network ports 1558-1, 1558-2 operablyconnected to the transceiver 1542. The AP 360-3 includes a wired andwireless transceiver 1562, a controller 1564 operably connected to thetransceiver 1562 that includes a DHCP client 1596, an antenna 1566, anda network port 1568 operably connected to the transceiver 1542. Thewireless sensor 362-1 includes a wireless transceiver 1572, a controller1574 operably connected to the transceiver 1572 that includes a DHCPclient 1598, and an antenna 1576 operably connected to the transceiver1542. The transceivers 1532, 1542, 1552, 1562, 1572, 1582 may be thesame as or similar to the transceivers 932, 982 depicted in FIG. 9 . Thecontrollers 1534, 1544, 1554, 1564, 1574, 1584 may be the same as orsimilar to the controllers 934, 984 depicted in FIG. 9 . The networkports 1538-1, 1538-2, 1548-1, 1548-2, 1558-1, 1558-2, 1568, 1588 may bethe same as or similar to the network ports 938, 988 depicted in FIG. 9. The antennae 1566, 1576 may be the same as or similar to the antennae936, 986 depicted in FIG. 9 . In some embodiments, the DHCP server 1540is configured to assign IP addresses and/or provide other networkinformation (e.g., an IP address of a DNS server, an IP address ofanother network device (e.g., an intermediate device), and/or a cloudserver address) to the DHCP clients 1590, 1592, 1594, 1596, 1598 and theDHCP clients 1590, 1592, 1594, 1596, 1598 are configured to request IPaddress and other information from the DHCP server 1540.

In some embodiments, routing in an NSB (e.g., the NSB 150 depicted inFIG. 1 or the NSB 350 depicted in FIG. 3 ) is achieved by the followingmechanisms. An OSPF routing protocol runs on each distribution switch(DS) and each access switch (AS). An OSPF module on a DS may advertisethe distribution switch loopbacks and the HE loopback IP addresses to acorresponding AS. An OSPF module on an AS may advertise the accessswitch loopbacks and access point loopbacks to a corresponding DS. An ASmay learn the AP loopbacks by DHCP snooping the DHCP response to acorresponding access point. An OSPF module on an AS may also advertisesthe access switch loopbacks to other access switches in the ring. HEsand APs may not run OSPF and may have a default route pointing tocorresponding DSs and ASs respectively. Each He may operate as an anchorfor all wireless and wired clients in the NSB architecture. APs and APsmay have GRE tunnels that terminate at corresponding HEs. All trafficfrom end-points connected to wired access switches and wireless accesspoints are tunneled to a HE. A HE may advertise all end-point IPaddresses using Generic Attribute Registration Protocol (GARP)/gRPC to acorresponding DS such that traffic received by the DS from an upstreamrouter can be forwarded to the appropriate head-end where a client isanchored. In some embodiments, failure and error conditions duringservice bring up are notified to an operator (e.g., the operator 120 ofthe installer device 106) via a combination of LEDs on network elementsand instructions on a mobile app of a device used by the operator. Oncenetwork services are automatically initiated for all network elements ofthe NSB, validation is performed for the NSB to make sure that the NSBconfiguration and topology are according to a planned design for thecustomer site.

FIG. 16 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.According to the method, at block 1602, from a network service server ata first network device of an NSB, network address information isobtained using a network service client at a second network device ofthe NSB that is connected with the first network device. In someembodiments, the network address information includes a network addressthat is assigned to the second network device by the network serviceserver at the first network device. In some embodiments, the networkservice server includes a dynamic host configuration protocol (DHCP)server, and the network service client includes a DHCP client. In someembodiments, the network address information includes an InternetProtocol (IP) address that is assigned to the DHCP client by the DHCPserver. At block 1604, at the second network device of the NSB, networkservice configuration information is obtained based on the networkaddress information. In some embodiments, the network addressinformation includes address information of a cloud server, and thenetwork service configuration information is obtained from the cloudserver based on the address information of the cloud server. In someembodiments, the network address information further includes an IPaddress of a DNS server. At block 1606, automatic network serviceinitiation of the second network device of the NSB is performed based onthe network service configuration information. In some embodiments,automatic network service initiation of an open shortest path first(OSPF) service or a link layer discovery protocol (LLDP) service in thesecond network device of the NSB is performed based on the networkservice configuration information. In some embodiments, the firstnetwork device of the NSB includes a distribution switch. In someembodiments, the second network device of the NSB includes a gateway, anaccess switch, a wireless access point, or a sensor. In someembodiments, the NSB includes a pair of distribution switches, a pair ofgateways that are connected to the distribution switches, a plurality ofaccess switches that are connected to the gateways, a plurality ofwireless access points (APs) that are connected to the access switches,and a plurality of wireless sensors that wirelessly connect to thewireless APs. The network service server may be similar to, the same as,or a component of the network service server 940 depicted in FIG. 9and/or the DHCP server 1540 depicted in FIG. 15 . The network serviceclient may be similar to, the same as, or a component of the networkservice client 990 depicted in FIG. 9 and/or the DHCP clients 1590,1592, 1594, 1596, 1598 depicted in FIG. 15 . The NSB may be similar to,the same as, or a component of the NSB 150 depicted in FIG. 1 and/or theNSB 350 depicted in FIG. 3 . The first network device may be similar to,the same as, or a component of the DSs 352-1, 352-2 of the NSB 350depicted in FIG. 3 , the network device 504 depicted in FIG. 5 , thefirst network device 904 depicted in FIG. 9 , and/or the DS 352-1depicted in FIG. 15 . The second network device may be similar to, thesame as, or a component of the HEs 354-1, 354-2 of the NSB 350, the ASs356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, 356-8, the wireless APs360-1, 360-2, 360-3, 360-4, 360-5, 360-6, and/or the wireless sensors362-1, 362-2, 362-3 depicted in FIG. 3 , the second network device 954depicted in FIG. 9 , and/or the HE 354-1, the ASs 356-1, 356-4, thewireless AP 360-3, and/or the wireless sensor 362-1 depicted in FIG. 15. The cloud server may be similar to, the same as, or a component of thecloud server 102 depicted in FIG. 1 .

FIG. 17 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.According to the method, at block 1702, automatic network serviceinitiation of a first network device of an NSB is performed to activatea network service server at the first network device. At block 1704, atthe network service server at the first network device, a request fornetwork address information is received from a network service client ata second network device of the NSB that is connected with the firstnetwork device. In some embodiments, the network service server includesa DHCP server, and the network service client includes a DHCP client. Insome embodiments, the network address information includes an IP addressthat is assigned to the DHCP client by the DHCP server. In someembodiments, automatic network service initiation of a DHCP service, anopen shortest path first (OSPF) service, and a link layer discoveryprotocol (LLDP) service in the first network device of the NSB isperformed. At block 1706, the network address information is transmittedfrom the network service server at the first network device to thenetwork service client at the second network device, where automaticnetwork service initiation of the second network device of the NSB isperformed based on the network address information. In some embodiments,the first network device of the NSB is paired with an installer deviceat a customer site to obtain first network service configurationinformation from the installer device. In some embodiments, automaticnetwork service initiation of the first network device of the NSB isperformed to activate the network service server at the first networkdevice based on the first network service configuration information fromthe installer device. The network service server may be similar to, thesame as, or a component of the network service server 940 depicted inFIG. 9 and/or the DHCP server 1540 depicted in FIG. 15 . The networkservice client may be similar to, the same as, or a component of thenetwork service client 990 depicted in FIG. 9 and/or the DHCP clients1590, 1592, 1594, 1596, 1598 depicted in FIG. 15 . The NSB may besimilar to, the same as, or a component of the NSB 150 depicted in FIG.1 and/or the NSB 350 depicted in FIG. 3 . The first network device maybe similar to, the same as, or a component of the DSs 352-1, 352-2 ofthe NSB 350 depicted in FIG. 3 , the network device 504 depicted in FIG.5 , the first network device 904 depicted in FIG. 9 , and/or the DS352-1 depicted in FIG. 15 . The second network device may be similar to,the same as, or a component of the HEs 354-1, 354-2 of the NSB 350, theASs 356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, 356-8, the wirelessAPs 360-1, 360-2, 360-3, 360-4, 360-5, 360-6, and/or the wirelesssensors 362-1, 362-2, 362-3 depicted in FIG. 3 , the second networkdevice 954 depicted in FIG. 9 , and/or the HE 354-1, the ASs 356-1,356-4, the wireless AP 360-3, and/or the wireless sensor 362-1 depictedin FIG. 15 .

FIG. 18 is a process flow diagram of a method of automatic networkservice initiation in accordance to an embodiment of the invention.According to the method, at block 1802, automatic network serviceinitiation of a first network device of an NSB is performed to activatea network service server at the first network device. At block 1804,from the network service server at the first network device, networkaddress information is obtained using a network service client at asecond network device of the NSB that is connected with the firstnetwork device. In some embodiments, the network service server includesa DHCP server, and the network service client includes a DHCP client. Insome embodiments, the network address information includes an IP addressthat is assigned to the DHCP client by the DHCP server. At block 1806,at the second network device of the NSB, network service configurationinformation is obtained based on the network address information. Atblock 1808, automatic network service initiation of the second networkdevice of the NSB is performed based on the network serviceconfiguration information. In some embodiments, automatic networkservice initiation of an open shortest path first (OSPF) service or alink layer discovery protocol (LLDP) service in the second networkdevice of the NSB is performed based on the network serviceconfiguration information. The network service server may be similar to,the same as, or a component of the network service server 940 depictedin FIG. 9 and/or the DHCP server 1540 depicted in FIG. 15 . The networkservice client may be similar to, the same as, or a component of thenetwork service client 990 depicted in FIG. 9 and/or the DHCP clients1590, 1592, 1594, 1596, 1598 depicted in FIG. 15 . The NSB may besimilar to, the same as, or a component of the NSB 150 depicted in FIG.1 and/or the NSB 350 depicted in FIG. 3 . The first network device maybe similar to, the same as, or a component of the DSs 352-1, 352-2 ofthe NSB 350 depicted in FIG. 3 , the network device 504 depicted in FIG.5 , the first network device 904 depicted in FIG. 9 , and/or the DS352-1 depicted in FIG. 15 . The second network device may be similar to,the same as, or a component of the HEs 354-1, 354-2 of the NSB 350, theASs 356-1, 356-2, 356-3, 356-4, 356-5, 356-6, 356-7, 356-8, the wirelessAPs 360-1, 360-2, 360-3, 360-4, 360-5, 360-6, and/or the wirelesssensors 362-1, 362-2, 362-3 depicted in FIG. 3 , the second networkdevice 954 depicted in FIG. 9 , and/or the HE 354-1, the ASs 356-1,356-4, the wireless AP 360-3, and/or the wireless sensor 362-1 depictedin FIG. 15 .

Although the operations of the method(s) herein are shown and describedin a particular order, the order of the operations of each method may bealtered so that certain operations may be performed in an inverse orderor so that certain operations may be performed, at least in part,concurrently with other operations. In another embodiment, instructionsor sub-operations of distinct operations may be implemented in anintermittent and/or alternating manner.

It should also be noted that at least some of the operations for themethods described herein may be implemented using software instructionsstored on a computer useable storage medium for execution by a computer.As an example, an embodiment of a computer program product includes acomputer useable storage medium to store a computer readable program.

The computer-useable or computer-readable storage medium can be anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system (or apparatus or device). Examples ofnon-transitory computer-useable and computer-readable storage mediainclude a semiconductor or solid-state memory, magnetic tape, aremovable computer diskette, a random-access memory (RAM), a read-onlymemory (ROM), a rigid magnetic disk, and an optical disk. Currentexamples of optical disks include a compact disk with read only memory(CD-ROM), a compact disk with read/write (CD-R/W), and a digital videodisk (DVD).

Alternatively, embodiments of the invention may be implemented entirelyin hardware or in an implementation containing both hardware andsoftware elements. In embodiments which use software, the software mayinclude but is not limited to firmware, resident software, microcode,etc.

Although specific embodiments of the invention have been described andillustrated, the invention is not to be limited to the specific forms orarrangements of parts so described and illustrated. The scope of theinvention is to be defined by the claims appended hereto and theirequivalents.

What is claimed is:
 1. A method of automatic network service initiation,the method comprising: pairing a first network device of a networkservice block (NSB) with an installer device at a customer site; at thefirst network device of the NSB, obtaining first network serviceconfiguration information from the installer device, wherein the firstnetwork service configuration information comprises a fully qualifieddomain name (FQDN) of a cloud server, an Internet Protocol (IP) addressof a domain name system (DNS) server, an IP address of a loopbackinterface, a peer device loopback interface IP address, and a dynamichost configuration protocol (DHCP) address scope; at the first networkdevice of the NSB, obtaining open shortest path first (OSPF) and linklayer discovery protocol (LLDP) configuration information from the cloudserver based on the first network service configuration information;performing automatic network service initiation of the first networkdevice of the NSB based on the first network service configurationinformation and the OSPF and LLDP configuration information; at a secondnetwork device of the NSB that is connected with the first networkdevice of the NSB, obtaining address information of a cloud server fromthe first network device of the NSB; at the second network device of theNSB, requesting second network service configuration information fromthe cloud server from a network address that is assigned to the secondnetwork device by the first network device; at the second network deviceof the NSB, obtaining the second network service configurationinformation from the cloud server based on the address information,wherein the second network service configuration information includesOSPF configuration or LLDP configuration for the second network device;and performing automatic network service initiation of the secondnetwork device of the NSB based on the second network serviceconfiguration information.
 2. The method of claim 1, wherein pairing thefirst network device of the NSB with the installer device at thecustomer site comprises pairing the first network device of the NSB withthe installer device at the customer site through a Bluetooth connectionbetween the first network device of the NSB and the installer device. 3.The method of claim 1, wherein the first network device of the NSBcomprises a distribution switch.
 4. The method of claim 3, wherein thesecond network device of the NSB comprises a gateway, an access switch,a wireless access point, or a sensor.
 5. The method of claim 1, whereinthe NSB comprises a pair of distribution switches, a pair of gatewaysthat are connected to the pair of distribution switches, a plurality ofaccess switches that are connected to the pair of gateways, a pluralityof wireless access points (APs) that are connected to the accessswitches, and a plurality of wireless sensors that wirelessly connect tothe wireless APs.
 6. The method of claim 1, wherein performing automaticnetwork service initiation of the first network device of the NSB basedon the first network service configuration information comprisesperforming automatic network service initiation of a DHCP service, anOSPF service, and an LLDP service in the first network device of the NSBbased on the first network service configuration information.
 7. Themethod of claim 1, wherein performing automatic network serviceinitiation of the second network device of the NSB based on the secondnetwork service configuration information comprises performing automaticnetwork service initiation of an OSPF service or an LLDP service in thesecond network device of the NSB based on the second network serviceconfiguration information.
 8. The method of claim 1, further comprisingat the first network device of the NSB, obtaining further networkservice configuration information from the cloud server based on thefirst network service configuration information.
 9. The method of claim1, wherein pairing the first network device of the NSB with theinstaller device at the customer site comprises pairing the firstnetwork device of the NSB with the installer device using a mobileapplication in the installer device at the customer site through ashort-range connection between the first network device of the NSB andthe installer device.
 10. A method of automatic network serviceinitiation, the method comprising: receiving information regardingdeploying a network service block (NSB) at a customer site at a mobileapplication of an installer device; at the customer site, pairing afirst network device of the NSB with the mobile application of theinstaller device through a wireless connection between the first networkdevice of the NSB and the installer device; and from the installerdevice, transmitting first network service configuration information tothe first network device of the NSB, wherein open shortest path first(OSPF) and link layer discovery protocol (LLDP) configurationinformation is obtained at the first network device of the NSB from acloud server based on the first network service configurationinformation, wherein automatic network service initiation of the firstnetwork device of the NSB is performed based on the first networkservice configuration information and the OSPF and LLDP configurationinformation, wherein the first network service configuration informationcomprises a fully qualified domain name (FQDN) of the cloud server, anInternet Protocol (IP) address of a domain name system (DNS) server, anIP address of a loopback interface, a peer device loopback interface IPaddress, and a dynamic host configuration protocol (DHCP) address scope,wherein at the second network device of the NSB, second network serviceconfiguration information is requested from the cloud server from anetwork address that is assigned to the second network device by thefirst network device, wherein the second network service configurationinformation is transmitted from the cloud server to a second networkdevice of the NSB, and wherein the second network service configurationinformation includes OSPF configuration or LLDP configuration for thesecond network device.
 11. The method of claim 10, wherein automaticnetwork service initiation of a DHCP service, an OSPF service, and anLLDP service in the first network device of the NSB is performed basedon the first network service configuration information.
 12. The methodof claim 10, wherein automatic network service initiation of secondnetwork devices of the NSB that are connected to the first networkdevice of the NSB is performed after automatic network serviceinitiation of the first network device of the NSB is performed.
 13. Amethod of automatic network service initiation, the method comprising:at a cloud server, receiving a request for first network serviceconfiguration information from a first network device of a networkservice block (NSB); at the cloud server, transmitting the first networkservice configuration information to the first network device of theNSB, wherein open shortest path first (OSPF) and link layer discoveryprotocol (LLDP) configuration information is obtained at the firstnetwork device of the NSB from the cloud server based on the firstnetwork service configuration information, wherein automatic networkservice initiation of the first network device of the NSB is performedat a customer site based on the first network service configurationinformation and the OSPF and LLDP configuration information, and whereinthe first network service configuration information comprises a fullyqualified domain name (FQDN) of a cloud server, an Internet Protocol(IP) address of a domain name system (DNS) server, an IP address of aloopback interface, a peer device loopback interface IP address, and adynamic host configuration protocol (DHCP) address scope; afterautomatic network service initiation of the first network device of theNSB is performed, at the cloud server, receiving a request for secondnetwork service configuration information from a second network deviceof the NSB that is connected to the first network device from a networkaddress that is assigned to the second network device by the firstnetwork device; and at the cloud server, transmitting the second networkservice configuration information to the second network device of theNSB, wherein the second network service configuration informationincludes OSPF configuration or LLDP configuration for the second networkdevice, and wherein automatic network service initiation of the secondnetwork device of the NSB is performed at the customer site based on thesecond network service configuration information.
 14. The method ofclaim 13, wherein automatic network service initiation of a DHCPservice, an OSPF service, and an LLDP service in the first networkdevice of the NSB is performed based on the first network serviceconfiguration information.
 15. The method of claim 13, wherein automaticnetwork service initiation of an OSPF service or an LLDP service in thesecond network device of the NSB is performed based on the secondnetwork service configuration information.
 16. The method of claim 13,wherein the first network device of the NSB comprises a distributionswitch.
 17. The method of claim 13, wherein the second network device ofthe NSB comprises a gateway, an access switch, a wireless access point,or a sensor.
 18. The method of claim 13, wherein the NSB comprises apair of distribution switches, a pair of gateways that are connected tothe pair of distribution switches, a plurality of access switches thatare connected to the pair of gateways, a plurality of wireless accesspoints (APs) that are connected to the access switches, and a pluralityof wireless sensors that wirelessly connect to the wireless APs.
 19. Themethod of claim 13, wherein at the cloud server, receiving the requestfor the second network service configuration information from the secondnetwork device of the NSB that is connected to the first network devicecomprises after the automatic network service initiation of the firstnetwork device of the NSB is performed, receiving the request for thesecond network service configuration information from the second networkdevice of the NSB with a network address that is assigned to the secondnetwork device by the first network device.